• I'm the package's author and/or maintainer.
• I have have read [the docs][1].
• I have tagged a release with a [semver][2] version number.
• My package repo has a description and a README describing what it's for and how to use it.
• My package doesn't add context menu entries. *
• My package doesn't add key bindings. **
• Any commands are available via the command palette.
• Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.
• If my package is a syntax it doesn't also add a color scheme. ***
• If my package is a syntax it is named after the language it supports (without suffixes like "syntax" or "highlighting").
• I use [.gitattributes][3] to exclude files from the package: images, test files, sublime-project/workspace.

ST's built-in bookmark system is commonly known to be deficient. There are several packages
that claim to improve on it but those I've used tend to be over-featured and/or brittle.
e.g. https://packagecontrol.io/packages/Better%20Bookmarks which is over-complicated
and hasn't been updated in 6 years.

• The basics toggle/next/previous/clear.
• Persisted per ST project.
• Option to traverse just the current file or all files in project.

This is one of several plugins I'm submitting to Package Control for consideration. I've been
refining them for several years and use them daily. I think they could be useful to others, in whole or as parts.